System, method, and computer program for providing similar product recommendations for non-merchant publishers based on publisher preferences

ABSTRACT

The present disclosure relates to a system, method, and computer program for automatically providing similar product recommendations for sold-out products promoted on non-merchant publisher sites, wherein the similar product recommendations are filtered for publisher preferences. A computer system with a product database provides a platform that enables non-merchant publishers to search products in the database, create call-to-actions on publisher sites for products in the database, and automatically receive similar product recommendations when end users of the publisher sites attempt to purchase promoted products that are now sold out. Once a publisher creates a call-to-action for a product that subsequently becomes sold out, similar product recommendations are provided without requiring any action on the publisher&#39;s part to change the publisher&#39;s site. Similar product recommendations are tailored to each publisher to account for publisher preferences. Publisher preferences may be learned by the system based on publisher behavior or inputted by each publisher.

RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 62/884,627 filed on Aug. 8, 2019, and titled “System, Method, and Computer Program for Providing Similar Product Recommendations for Non-Merchant Publishers based on Publisher Preferences,” the contents of which are incorporated by reference herein as if fully disclosed herein.

BACKGROUND OF THE INVENTION 1. Field of the Invention

This invention relates generally to ecommerce systems, and, more specifically, to a system that provides similar product recommendations for non-merchant publishers based on publisher preferences.

2. Description of the Background Art

The role of influencers and bloggers in commerce is growing rapidly. Many shoppers, especially younger generations, prefer to purchase products that are vetted and recommended by a trusted influencer. Certain providers of digital shopping platforms, such as SHOPSTYLE, maintain product databases and search engines that are accessible to third-party, non-merchant publishers (e.g., bloggers, influencers, etc.). Non-merchant publishers are able to search the product database and insert links to products in the database in their sites. When a user of a publisher site clicks on a linked product, the user is redirected to the applicable merchant webpage for the product. The user's shopping session on the merchant's site is associated with the digital shopping platform, which receives a commission for any sale made during the session, and in turn passes a share of it to the publisher.

The Internet “shelf life” of blog posts (or other non-merchant publisher posts) tend to be significantly longer than the availability of the products recommended in the posts. Therefore, when a product referenced in a post is sold out, it would be helpful to provide the user with similar product recommendations.

SUMMARY OF THE DISCLSOURE

The present disclosure relates to a system, method, and computer program for automatically providing similar product recommendations for sold-out products promoted on non-merchant publisher sites, wherein the similar product recommendations are filtered for publisher preferences. A computer system with a product database provides a platform that enables non-merchant publishers to search products in the database, create call-to-actions (e.g., a “buy” button) on publisher sites for products in the database, and automatically receive similar product recommendations when end users of the publisher sites attempt to purchase promoted products that are now sold out. Once a publisher creates a call-to-action for a product that subsequently becomes sold out, similar product recommendations are provided without requiring any action on the publisher's part to change the publisher's site. Similar product recommendations are tailored to each publisher to account for publisher preferences. In certain embodiments, publisher preferences are learned by the system based on publisher behavior, and in other embodiments, publisher preferences are inputted by each publisher.

In one embodiment, providing the platform comprises the following steps:

-   -   maintaining a product database with products from a plurality of         merchants, wherein each product entry in the database is         associated with a product ID, an associated merchant, a link to         a webpage on the associated merchant's site, and an indicator of         whether the product is in stock at the associated merchant;     -   providing a user interface to the product database that enables         a plurality of non-merchant publishers, each associated with a         different non-merchant publisher site, to search the product         database and to create call-to-actions on the different         non-merchant publisher sites with respect to products in the         product database;     -   providing an application programming interface to the system         that enables the system to receive call-to-action selections         from end users of the different non-merchant publisher sites         with respect to products in the product database;     -   receiving, at the application programming interface,         call-to-action selections from end users on the different         non-merchant publisher sites for products in the product         database that are out-of-stock, wherein the call-to-action         selections are entered through the non-merchant publisher sites         and transmitted by client applications running the non-merchant         publisher sites;     -   for each of the call-to-action selections received for products         that are out of stock, performing the following:         -   identifying a plurality of similar products to the             out-of-stock product in the product database by comparing             product images and/or product metadata in the product             database;         -   filtering the identified similar products by one or more             publisher preferences specific to the non-merchant publisher             associated with the call-to-action selection; and         -   enabling the end user that made the call-to-action selection             to view information on one or more of the filtered and             identified similar products.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-B are flowcharts that illustrate a method, according to one embodiment, for providing similar product recommendations on a digital shopping platform accessible to multiple non-merchant publishers.

FIG. 2 is a flowchart that illustrates an example implementation of the method of FIG. 1 in which product widgets are used to display product information and initiate call-to-action requests.

FIG. 3 is a flowchart that illustrates an alternate example implementation of the method of FIG. 1.

FIG. 4 is a block diagram that illustrates an example system architecture.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present disclosure relates to a system, method, and computer program for automatically providing similar product recommendations for sold-out products promoted on non-merchant publisher sites, wherein the similar product recommendations are filtered for publisher preferences. Specifically, a digital shopping platform is provided that enables third-party, non-merchant publishers to search a product database with products from multiple merchants, create call-to-actions on the non-merchant publisher sites with respect to products in the database, and automatically receive similar product recommendations when end users of the publisher sites attempt to purchase promoted products in the database that are now sold out. Once a publisher creates a call-to-action for a product that subsequently becomes sold out, similar product recommendations are provided without requiring any action on the publisher's part to change the publisher's site. The platform is accessible to multiple non-merchant publishers that promote merchant products. The method is performed by a computer system (“the system”). The term “publisher” herein references to non-merchant publishers that promote third party merchant products. A “publisher site” is a publisher's website or mobile application content.

FIGS. 1A-B illustrate a method for providing similar product recommendations on a digital shopping platform accessible to multiple non-merchant publishers. The system maintains a product database with products from a plurality of merchants (step 110). In one embodiment, each product entry is associated with a product ID, a product title and/or description, a product image, an associated merchant, a link to a webpage on the associated merchant's site, and an indicator of whether the product is in stock at the associated merchant.

The system provides a publisher user interface to the product database that enables a plurality of non-merchant publishers, each associated with a different publisher site, to register with the system, access the product database, and create call-to-actions on the different publisher sites with respect to products in the product database (step 120). An example of a call-to-action is a “buy” button or link that redirects an end user of the non-merchant publisher site to a merchant product webpage from which the end user can purchase a product promoted on the publisher's site.

The system provides an application programming interface (API) that enables the system to receive, via client applications running non-merchant publishers' sites, call-to-action selections on non-merchant publisher sites from the end users with respect to products in the product database (step 130). An end user initiates the call-to-action from a non-merchant publisher site. The system can receive call-to-action requests from many different non-merchant publisher sites. Examples of client applications that can run non-merchant publisher sites are web browsers and mobile applications.

In response to receiving a call-to-action request to purchase a product, the system determines whether the product is in stock at the merchant associated with the product (steps 135, 140). If so, the system redirects the end user's client application (e.g., web browser) to a page on the merchant's site for the product (step 145). The end user's shopping session on the merchant's site is associated with the system, which typically provides the publisher with a share of any commission received from the merchant for product(s) purchased during the session.

In response to receiving a call-to-action to purchase a product that is out-of-stock, the system identifies a plurality of similar products to the out-of-stock product in the product database by comparing product images and/or product metadata in the product database (step 150). For example, the system may search the product database for products with similar metadata or the same GTIN number (a 14-digit number that is used to identify trade items, products or services). Visual image analysis of product images may be used to identified similar products. The visual image analysis may be performed by the system or by a third-party source. In one embodiment, the system uses a combination of metadata searches and visual image analysis to identify similar products.

Identifying a plurality of similar products in step 150 may mean identifying similar products in real-time or retrieving information for previously-identified similar products. In certain embodiments, the system may identify the similar products in advance of receiving the call-to-action request and then retrieve information about the identified similar products in response to receiving the call-to-action request. For example, system may track the products in the database for which non-merchant publishers have created call-to-actions, and, in response to any of these products going out of stock, identify similar products and cache this information for quick retrieval upon receiving a call-to-action request.

The system filters the identified similar products by one or more publisher preferences specific to the non-merchant publisher associated with the call-to-action request (step 160). In one embodiment, the publisher preferences are explicit preferences specified by the publisher when the publisher registers with the system or updates his/her profile in the system. In an alternate embodiment, the system ascertains publisher preferences based on past publisher behavior. For example, the system may track the merchants associated with products in the product database to which the publisher links, the typical price range of products to which the publisher links, the type of products, etc. The system may filter out identified similar products that are inconsistent with the publisher's past behavior. For example, the system may filter out identified similar products from merchants to whom the publisher has never linked or filter products that are outside a price range of products typically promoted by the publisher. After filtering the similar product search results by one or more publisher preferences, the system enables the end user that made the call-to-action selection to view information on one or more of the filtered and identified similar products (step 170).

In certain embodiments, the system enables publishers to create call-to-actions for products in the product database using “product widgets.” Product widgets are software code that enable certain functionality in a web browser or mobile application with respect to products associated with the widget. For example, a product widget may display a product image, a title or brief description, and a “buy” button for purchasing the displayed product, and it may initiate the call-to-action request to the system in response to an end user selecting the “buy” button.

In certain embodiments, the system provides a user interface for publishers that enables them to create instances of widgets and associate them with products in the product database. The user interface displays one or more widgets. Each widget type may display product information differently. The user interface enables the publisher to select a widget and associate one or more products in the product database with an instance of the selected widget. Each instance of a widget has a unique widget ID. Each widget ID is mapped to product identifiers for the products associated with the instance of the widget. The widget ID also is associated with a publisher ID for the publisher that created the instance of the widget. The user interface enables the publisher to copy the software code for the instance of the widget. The publisher can then incorporate the code into the publisher's website or mobile application.

FIG. 2 illustrates an example implementation of the method of FIG. 1 in which product widgets are used to display product information and initiate call-to-action requests. In response to an end user loading the publisher's site into a browser or opening a publisher's mobile application, a product widget in the publisher's site initializes and provides its widget ID to the system (steps 210, 220). As discussed above, each widget ID is associated with one or more product IDs, and the system identifies the product IDs associated with the widget ID (step 230).

The system retrieves product metadata associated with each of the identified product IDs (step 240). The metadata may include an image of the product, the brand of the product, a title or brief description of the product, the merchant selling the product, the price, and the current availability (i.e., in stock or out of stock). The metadata may be retrieved from a cached index of products or the product database. The system provides some or all of the product metadata to the requesting widget (step 250).

The widget uses the product metadata to display product information on the publisher sites (step 260). For example, for each product associated with the widget, the widget may display an image of the product, a title, and a price. The widget also displays a call-to-action, such as a “buy” button, for each product associated with the widget. The widget may display the product information and call-to-action directly on the publisher's site or within a frame/window on the site.

In response to a user selecting a call-to-action to purchase a product, the widget notifies the system of the call-to-action selection, along with the associated product ID (step 270). The system uses the product ID to look up availability information in the product database or a cached product index. If the product is in stock, the server redirects the user's browser to the merchant webpage associated with the product ID (step 280). If the product is out-of-stock, the system notifies the widget and provides the widget with metadata for similar products within the product database that have been filtered for publisher preferences (also step 280). As discussed above, similar products may be identified by searching product metadata within the system and/or doing visual analysis to identify similar-looking products.

In response to receiving notification that a product is out-of-stock, the widget indicates the product is out-of-stock on the publisher's site (step 290). For example, the widget may display a notice that the product is out-of-stock, as well as a call-to-action that enables a user to see similar products. If the user clicks on the call-to-action to see similar products, the widget displays a window/frame/modal window (e.g., an iframe) with similar products. Each similar product is displayed with a call-to-action for buying the product. If a user clicks on a call-to-action for a similar product, the system repeats steps 280 and, if applicable, 290 for the similar product.

In certain embodiments, the system notifies a widget of any out-of-stock products associated with the widget upon the widget initializing. In such cases, the call-to-action initially displayed by the widget on the publisher's site may be a call-to-action to see similar products.

FIG. 3 illustrates an alternate implementation of the method of FIG. 1. In this implementation, the system enables users to create links to products in the product database and incorporate the links directly into the publisher site in the form of call-to-actions (e.g., a “buy” button). In response to a user clicking on a call-to-action to purchase a product on the publisher site, the user's client application (e.g., a web browser or mobile app), notifies the system of the call-to-action and provides the associated product ID (steps 310, 320, and 330). The system then determines if the product is in stock by using the product ID to look up product information in a cached product index or the product database (step 340). If the product is in stock at the merchant associated with the product ID, the server retrieves the applicable merchant webpage address for the product (step 350). If the product is out of stock, the system creates a webpage with similar products from the product database that have been filtered for publisher preferences (also step 350). The system then redirects the client application to the merchant website or the similar products page, depending on whether the product is in stock (step 360). The client application displays the merchant webpage or similar products webpage, whichever is applicable (step 370). If the user selects a product in the similar products webpage that is also out-of-stock, steps 350-370 are repeated with respect to the selected similar product. Also, the similar products may be filtered for availability in addition to publisher preferences.

FIG. 4 illustrates an example system architecture. The system includes a product database 470 and a server 410 that runs a plurality of software modules. The software modules include the following:

-   -   Publisher UI module 460 for generating the user interfaces that         enable the publisher to register with the system and search the         product database.     -   Widget UI module 435 for generating the user interfaces that         enable publishers to create widgets or call-to-actions to         products in the product database 470.     -   Database interface module 440 for searching, retrieving, and         storing information in the product database 470.     -   API 455 for receiving and processing call-to-action requests         from client applications displaying publisher sites.     -   Similar Product Identifier module 445 for identify similar         products to an out-of-stock product. Module 445 may interface         with third party systems, such as system that identify similar         products based on image analysis.     -   Publisher Preference Filter module 450 for filtering similar         products based on learned or explicit publisher preferences.

Server 410 interfaces with publisher sites 420 and merchant websites 430 for the purpose of providing product information to end users, processing call-to-action requests, and redirecting customers to merchants' sites, as described above.

The methods described herein may be implemented in a system configured differently and are not limited to the system architecture illustrated in FIG. 4.

The methods described herein are embodied in software and performed by a computer system (comprising one or more computing devices) executing the software. A person skilled in the art would understand that a computer system has one or more memory units, disks, or other physical, computer-readable storage media for storing software instructions, as well as one or more processors for executing the software instructions.

As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Accordingly, the above disclosure is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims. 

1. A method, performed by a computer system, for enabling similar product recommendations on a plurality of non-merchant publisher sites that promote merchant products, wherein the non-merchant publishers are not affiliated with the merchants and wherein the similar product recommendations are for sold-out products, the method comprising: maintaining a product database with products from a plurality of merchants, wherein each product entry in the database is associated with a product ID, an associated merchant, a link to a webpage on the associated merchant's site, and an indicator of whether the product is in stock at the associated merchant; providing a user interface to the product database that enables a plurality of non-merchant publishers, each associated with a different non-merchant publisher site, to search the product database and to create call-to-actions on the different non-merchant publisher sites with respect to products in the product database; providing an application programming interface to the system that enables the system to receive call-to-action selections from end users of the different non-merchant publisher sites with respect to products in the product database; receiving, at the application programming interface, call-to-action selections from end users on the different non-merchant publisher sites for products in the product database that are out-of-stock, wherein the call-to-action selections are entered through the non-merchant publisher sites and transmitted by client applications running the non-merchant publisher sites; for each of the call-to-action selections received for products that are out of stock, performing the following: identifying a plurality of similar products to the out-of-stock product in the product database by comparing product images and/or product metadata in the product database; filtering the identified similar products by one or more publisher preferences specific to the non-merchant publisher associated with the call-to-action selection; and enabling the end user that made the call-to-action selection to view information on one or more of the filtered and identified similar products.
 2. The method of claim 1, wherein the publisher preferences for a non-merchant publisher are determined by the system based on the non-merchant publisher's prior behavior.
 3. The method of claim 1, wherein the publisher preferences for a non-merchant publisher are based on explicit preferences provided to the system by the non-merchant publisher.
 4. The method of claim 1, wherein the one or more publisher preferences include a merchant category or group of merchants associated with the non-merchant publisher site from which the call-to-action request was initiated, wherein the system filters out similar products from merchants outside the merchant category or group.
 5. The method of claim 1, wherein providing the user interface that enables the non-merchant publisher to create call-to-action comprises providing a user interface in which a non-merchant publisher can create a product widget, associate the product widget with one or more products in the product database, and embed the product widget in the non-merchant publisher site.
 6. A non-transitory computer-readable medium comprising a computer program that, when executed by a computer system, enables the computer system to perform the following method for enabling similar product recommendations on a plurality of non-merchant publisher sites that promote merchant products, wherein the non-merchant publishers are not affiliated with the merchants and wherein the similar product recommendations are for sold-out product, the method comprising: maintaining a product database with products from a plurality of merchants, wherein each product entry in the database is associated with a product ID, an associated merchant, a link to a webpage on the associated merchant's site, and an indicator of whether the product is in stock at the associated merchant; providing a user interface to the product database that enables a plurality of non-merchant publishers, each associated with a different non-merchant publisher site, to search the product database and to create call-to-actions on the different non-merchant publisher sites with respect to products in the product database; providing an application programming interface to the system that enables the system to receive call-to-action selections from end users of the different non-merchant publisher sites with respect to products in the product database; receiving, at the application programming interface, call-to-action selections from end users on the different non-merchant publisher sites for products in the product database that are out-of-stock, wherein the call-to-action selections are entered through the non-merchant publisher sites and transmitted by client applications running the non-merchant publisher sites; for each of the call-to-action selections received for products that are out of stock, performing the following: identifying a plurality of similar products to the out-of-stock product in the product database by comparing product images and/or product metadata in the product database; filtering the identified similar products by one or more publisher preferences specific to the non-merchant publisher associated with the call-to-action selection; and enabling the end user that made the call-to-action selection to view information on one or more of the filtered and identified similar products.
 7. The non-transitory computer-readable medium of claim 6, wherein the publisher preferences for a non-merchant publisher are determined by the system based on the non-merchant publisher's prior behavior.
 8. The non-transitory computer-readable medium of claim 6, wherein the publisher preferences for a non-merchant publisher are based on explicit preferences provided to the system by the non-merchant publisher.
 9. The non-transitory computer-readable medium of claim 6, wherein the one or more publisher preferences include a merchant category or group of merchants associated with the non-merchant publisher site from which the call-to-action request was initiated, wherein the system filters out similar products from merchants outside the merchant category or group.
 10. The non-transitory computer-readable medium of claim 6, wherein providing the user interface that enables the non-merchant publisher to create call-to-action comprises providing a user interface in which a non-merchant publisher can create a product widget, associate the product widget with one or more products in the product database, and embed the product widget in the non-merchant publisher site.
 11. A computer system for enabling similar product recommendations on a plurality of non-merchant publisher sites that promote merchant products, wherein the non-merchant publishers are not affiliated with the merchants and wherein the similar product recommendations are for sold-out products, the system comprising: one or more processors; one or more memory units coupled to the one or more processors, wherein the one or more memory units store instructions that, when executed by the one or more processors, cause the system to perform the operations of: maintaining a product database with products from a plurality of merchants, wherein each product entry in the database is associated with a product ID, an associated merchant, a link to a webpage on the associated merchant's site, and an indicator of whether the product is in stock at the associated merchant; providing a user interface to the product database that enables a plurality of non-merchant publishers, each associated with a different non-merchant publisher site, to search the product database and to create call-to-actions on the different non-merchant publisher sites with respect to products in the product database; providing an application programming interface to the system that enables the system to receive call-to-action selections from end users of the different non-merchant publisher sites with respect to products in the product database; receiving, at the application programming interface, call-to-action selections from end users on the different non-merchant publisher sites for products in the product database that are out-of-stock, wherein the call-to-action selections are entered through the non-merchant publisher sites and transmitted by client applications running the non-merchant publisher sites; for each of the call-to-action selections received for products that are out of stock, performing the following: identifying a plurality of similar products to the out-of-stock product in the product database by comparing product images and/or product metadata in the product database; filtering the identified similar products by one or more publisher preferences specific to the non-merchant publisher associated with the call-to-action selection; and enabling the end user that made the call-to-action selection to view information on one or more of the filtered and identified similar products.
 12. The system of claim 11, wherein the publisher preferences for a non-merchant publisher are determined by the system based on the non-merchant publisher's prior behavior.
 13. The system of claim 11, wherein the publisher preferences for a non-merchant publisher are based on explicit preferences provided to the system by the non-merchant publisher.
 14. The system of claim 11, wherein the one or more publisher preferences include a merchant category or group of merchants associated with the non-merchant publisher site from which the call-to-action request was initiated, wherein the system filters out similar products from merchants outside the merchant category or group.
 15. The system of claim 11, wherein providing the user interface that enables the non-merchant publisher to create call-to-action comprises providing a user interface in which a non-merchant publisher can create a product widget, associate the product widget with one or more products in the product database, and embed the product widget in the non-merchant publisher site. 